Method and communication system for storing address of network anchor point to network server

ABSTRACT

A method, apparatus and communication system for registering address information of a network anchor point to a network server are disclosed. A network apparatus, such as a mobility management entity, determines whether to register address information of a network anchor point to a network server, and registers the address information of the network anchor point to the network server when determining to do so.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.13/915,877, filed on Jun. 12, 2013, which is a continuation of U.S.patent application Ser. No. 13/551,376, filed on Jul. 17, 2012, now U.S.Pat. No. 8,483,686, which is a continuation of U.S. patent applicationSer. No. 12/550,867, filed on Aug. 31, 2009, now U.S. Pat. No.8,244,242, which is a continuation of International Application No.PCT/CN2007/071260, filed on Dec. 18, 2007, which claims priority toChinese patent application No. 200710074594.0, filed on May 28, 2007,and Chinese patent application No. 200710140572.X, filed on Aug. 13,2007, all of which are hereby incorporated by reference in theirentireties.

TECHNICAL FIELD

The present disclosure relates to a wireless communication technology,particularly to a technology for storing and deleting an address of anetwork anchor point, and more particularly to a method andcommunication system for storing an address of a network anchor point toa network server.

BACKGROUND

For future communication technologies, it will be an important researchsubject to achieve a seamless handover of a terminal between 3^(rd)Generation Partnership Project (3GPP) and non-3GPP access technologies.

Currently, as the two access technologies are different in aspects suchas air interface, authentication, user plane establishment, and controlplane entities of core networks of the two access technologies have nocorresponding interface, a seamless handover of a terminal between the3GPP and non-3GPP access technologies is a hard forward handoverprocess, that is, an attachment process will be performed again when theterminal in an active state accesses a heterogeneous access network.

After the terminal is attached to an access network, the terminal mayselect a network anchor point for connection to an external packet datanetwork (PDN); and an Internet protocol (IP) address used by theterminal will be assigned by the network anchor point or provided by theexternal PDN. In the 3GPP access technology, an entity in a network mayobtain an address of the network anchor point by using an access pointname (APN); and in the non-3GPP access technology, the terminal mayobtain the address of the network anchor point during accessauthentication or obtain the address of the network anchor point from adomain name server (DNS) by using the APN obtained during the accessauthentication. Therefore, modes for obtaining an address of a networkanchor point are different for different access technologies. As such,when the terminal is attached to a 3GPP network, the terminal may selecta network anchor point, and obtain an address of the network anchorpoint. When the terminal in the active state moves from the 3GPP networkto a non-3GPP network, a reattachment process may be triggered, and aPDN gateway (PDN GW) reselection process needs to be triggered. If themode for obtaining an address of a network anchor point in the non-3GPPnetwork is used, the obtained network anchor point may not be a networkanchor point obtained in the 3GPP network, which causes a change inconnection of a user IP level, resulting in data loss. Therefore, whenthe terminal is handed over between different access networks, it isessential to keep the network anchor point unchanged in order tomaintain the service continuity.

In order to keep the network anchor point unchanged, those skilled inthe art proposed a concept: storing an address of a network anchor pointobtained in an access network to a network server; and obtaining theaddress of the network anchor point from the network server when theterminal is handed over from the access network to another accessnetwork. As such, no matter which network the terminal is handed overto, the same address of the network anchor point may be obtained, thusavoiding loss of user data.

However, currently, storing an address of a network anchor point to anetwork server is not feasible, nor is deleting an address of a networkanchor point from a network server feasible.

BRIEF SUMMARY

Various embodiments described herein provide a method and communicationsystem for storing an address of a network anchor point to a networkserver, so as to provide a feasible technical solution for storing anaddress of a network anchor point to a network server.

One embodiment of the present disclosure provides a method for storingan address of a network anchor point to a network server. The methodincludes the following steps.

A terminal initiates an attach request or a bearer establishmentrequest, and a network selects a network anchor point.

When the network anchor point assigns a first bearer context to theterminal, or when a first connection is established between the networkanchor point and the terminal, the network registers an address of thenetwork anchor point to a network server.

One embodiment of the present disclosure further provides acommunication system. The communication system includes a bearer contextassignment entity and an address registration entity. The bearer contextassignment entity is configured to enable a network anchor point toassign a first bearer context to a terminal. The address registrationentity is configured to register an address of the network anchor pointwith a network server when the network anchor point assigns the firstbearer context to the terminal.

One embodiment of the present disclosure further provides acommunication system. The communication system includes a connectionestablishment entity and an address registration entity. The connectionestablishment entity is configured to establish a first connectionbetween a network anchor point and a terminal. The address registrationentity is configured to register an address of the network anchor pointwith a network server when the first connection between the networkanchor point and the terminal is established.

Embodiments of the present disclosure also provide a method andcommunication system for deleting an address of a network anchor pointfrom a network server, so as to provide a feasible technical solutionfor deleting an address of a network anchor point from a network server,scenarios where a server entity in a network initiates a delete bearerrequest, and specific processes related thereof.

One embodiment of the present disclosure provides a method for deletingan address of a network anchor point from a network server. The methodincludes the following steps.

When a terminal or an entity in a network initiates a delete bearerrequest, the network instructs a network server to delete an address ofa network anchor point that has been registered with the network serverif the network anchor point no longer serves the terminal.

The network server deregisters the address of the network anchor point.

One embodiment of the present disclosure further provides acommunication system. The communication system includes an addressdeletion notification entity and an deregistration entity. The addressdeletion notification entity is configured to send a notification fordeleting an address of a network anchor point that has been registeredwith a network server and no longer serves a terminal when the terminalor an entity in a network initiates a Delete Bearer Request. Thederegistration entity is configured to deregister the address of thenetwork anchor point according to the notification of the addressdeletion notification entity.

A method for releasing a bearer is provided. The method includes thefollowing steps.

A network server initiates a bearer release request.

After receiving a bearer release response, the network server deletes anaddress of a network anchor point corresponding to the bearer stored onthe network server.

Embodiments of the present disclosure also provide a method for aterminal to log out of a network, so as to provide for a terminal to logout of a network and specific processes for a terminal to log out of anetwork.

The method includes the following steps.

A terminal logout process is triggered, and access network resourcescorresponding to the terminal are released.

A mobile Internet protocol (IP) binding corresponding to the terminal isunbound.

Address information of all network anchor points related to the terminalstored in a network server is deleted.

In some embodiments of the present disclosure, a network anchor pointmay assign a first bearer context to a terminal or a first connectionmay be established between the network anchor point and the terminal,and a network registers an address of the network anchor point with anetwork server. Thus, the embodiments of the present disclosure mayprovide a feasible technical solution for registering an address of anetwork anchor point with a network server.

In some other embodiments of the present disclosure, when a networkanchor point on longer serves a terminal, a network server may receive anotification for deleting an address of the network anchor point andthen deregister the address of the network anchor point. Thus, theembodiments of the present disclosure may provide a feasible embodimentfor deleting an address of a network anchor point from a network server,and a feasible embodiment for implementing a bearer release processinitiated by a network server.

In some other embodiments of the present disclosure, when it is requiredto break a connection between a terminal and a network, addressinformation of all network anchor points related to the terminal storedin a network server is deleted, and a mobile IP binding corresponding tothe terminal is unbound, so as to break the connection between theterminal and the network.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a schematic view of an evolved radio network architecture inthe prior art;

FIG. 2A and FIG. 2B together show a flow chart of a method for storingan address of a network anchor point to a network server according toone embodiment of the present disclosure;

FIG. 3A and FIG. 3B together show a flow chart of the method for storingan address of a network anchor point to a network server according toone embodiment of the present disclosure;

FIG. 4A and FIG. 4B together show a flow chart of the method for storingan address of a network anchor point to a network server according toone embodiment of the present disclosure;

FIG. 5 is a flow chart of the method for storing an address of a networkanchor point to a network server according to one embodiment of thepresent disclosure;

FIG. 6 is a flow chart of the method for storing an address of a networkanchor point to a network server according to one embodiment of thepresent disclosure;

FIG. 7 is a flow chart of the method for storing an address of a networkanchor point to a network server according to one embodiment of thepresent disclosure;

FIG. 8 is a flow chart of the method for storing an address of a networkanchor point to a network server according to one embodiment of thepresent disclosure;

FIG. 9 is a flow chart of an eighth preferred embodiment of the methodfor storing an address of a network anchor point to a network serveraccording to one embodiment of the present disclosure;

FIG. 10 is a flow chart of the method for storing an address of anetwork anchor point to a network server according to one embodiment ofthe present disclosure;

FIG. 11 is a flow chart of a method for deleting an address of a networkanchor point from a network server according to one embodiment of thepresent disclosure;

FIG. 12 is a flow chart of the method for deleting an address of anetwork anchor point from a network server according to one embodimentof the present disclosure;

FIG. 13 is a flow chart of the method for deleting an address of anetwork anchor point from a network server according to one embodimentof the present disclosure;

FIG. 14 is a flow chart of the method for deleting an address of anetwork anchor point from a network server according to one embodimentof the present disclosure;

FIG. 15 is a flow chart of the method for deleting an address of anetwork anchor point from a network server according to one embodimentof the present disclosure;

FIG. 16 is a flow chart of the method for deleting an address of anetwork anchor point from a network server according to one embodimentof the present disclosure;

FIG. 17 is a flow chart of the method for deleting an address of anetwork anchor point from a network server according to one embodimentof the present disclosure;

FIG. 18 is a flow chart of the method for deleting an address of anetwork anchor point from a network server according to one embodimentof the present disclosure;

FIG. 19 is a flow chart of the method for deleting an address of anetwork anchor point from a network server according to one embodimentof the present disclosure;

FIG. 20 is a flow chart of a method for implementing a bearer releaseprocess initiated by a network server according to one embodiment of thepresent disclosure;

FIG. 21 is a flow chart of the method for deleting an address of anetwork anchor point from a network server according to one embodimentof the present disclosure;

FIG. 22 is a flow chart of a method for a terminal to log out of anetwork according to one embodiment of the present disclosure;

FIG. 23 is a flow chart of the method for a terminal to log out of anetwork according to one embodiment of the present disclosure;

FIG. 24 is a flow chart of the method for a terminal to log out of anetwork according to one embodiment of the present disclosure;

FIG. 25 is a flow chart of the method for a terminal to log out of anetwork according to one embodiment of the present disclosure;

FIG. 26 is a flow chart of the method for a terminal to log out of anetwork according to one embodiment of the present disclosure;

FIG. 27 is a flow chart of the method for a terminal to log out of anetwork according to one embodiment of the present disclosure;

FIG. 28 is a flow chart of the method for a terminal to log out of anetwork according to one embodiment of the present disclosure;

FIG. 29 is a flow chart of the method for a terminal to log out of anetwork according to one embodiment of the present disclosure;

FIG. 30 is a flow chart of the method for a terminal to log out of anetwork according to one embodiment of the present disclosure;

FIG. 31 is a flow chart of the method for a terminal to log out of anetwork according to one embodiment of the present disclosure; and

FIG. 32 is a flow chart of the method for a terminal to log out of anetwork according to one embodiment of the present disclosure.

DETAILED DESCRIPTION OF THE EMBODIMENTS

As some embodiments described in the following relate to the evolvedradio network technology, a evolved radio network architecture isillustrated first with reference to FIG. 1.

As shown in FIG. 1, a core network of an evolved radio network mainlyincludes a mobility management entity (MME), a serving gateway (servingGW), a PDN GW, and other logic functional modules. The MME isresponsible for the mobility management of the control plane, includingthe management of user contexts and mobility states, the allocation oftemporary identities to users as well as security functions, andcorresponds to a control plane part of a serving GPRS support node(SGSN) in a current universal mobile telecommunication system (UMTS).The serving GW is a user plane entity responsible for initiating apaging for downlink data in an idle state, managing and storing IPbearer parameters and intra-network route information, and correspondsto a data plane part of a gateway GPRS support node (GGSN) and the SGSNin the current UMTS system. An evolved packet data gateway (ePDG) isequivalent to an access gateway of a non-3GPP network. The PDN GW isequivalent to a network anchor point between different access networks.An interface between the PDN GW and a 3GPP access network is S5 as shownin FIG. 1, and an interface between the PDN GW and a non-3GPP accessnetwork is S2 (not shown in FIG. 1).

In order to enable those skilled in the art to store an address of anetwork anchor point to a network server, several embodiments of thepresent disclosure are described in the following with reference to theaccompanying drawings.

Embodiments as shown in FIGS. 2A and 2B, 3A and 3B, and 4A and 4Brespectively describe processes for registering an address of a PDN GWwith a home subscriber server (HSS) when a terminal is attached to a3GPP access network.

Specifically, in the embodiment shown in FIG. 2A and FIG. 2B, an MMEregisters an address of a PDN GW with an HSS.

As shown in FIG. 2A and FIG. 2B, the process includes the followingsteps.

In Step S201, a user equipment (UE) initiates an Attach Request. Therequest contains an International Mobile Subscriber Identity (IMSI), anS-Temporary Mobile Subscriber Identity (S-TMSI), a Tracking AreaIdentity (TAI), a selected network identity, and other parameters.

In Step S202, an evolved Node B (eNodeB) forwards the Attach Request toa new MME. The Attach Request carries a cell identity. Specifically, theeNodeB may query an MME address from the selected network identity andthe S-TMSI, and may select an MME if the eNodeB cannot derive an MME.

In Step S203, the new MME sends an Identification Request to an old MMEto request an IMSI. The old MME may respond with an IdentificationResponse by providing the IMSI. After the UE is separated or detachedfrom the network, the S-TMSI of the UE and the MME are changed, and thenew MME may send the S-TMSI and old TAI to the old MME to request theIMSI.

In Step S204, if neither the new MME nor the old MME can identify theUE, the new MME sends an Identification Request to the UE to request theIMSI, and the UE may respond with an Identification Response byproviding the IMSI to the new MME.

In Step S205, if no context of the UE exists in the network, anAuthentication message must be performed forcedly.

In Step S206, if some active bearer contexts related to the UE exist inthe new MME, the new MME needs to send a Delete Bearer Request to arelated gateway (for example, the PDN GW as shown in the figure), andthe related gateway may respond with a Delete Bearer Response, so thatthe new MME deletes the bearer contexts.

In Step S207, the new MME sends an Update Location message to an HSS.The Update Location message contains an identity of the new MME and theIMSI.

In Step S208, the HSS sends a Cancel Location message to the old MME,and the old MME responds with a Cancel Location Acknowledgement (Ack)message and removes the mobility management and bearer contexts.

In Step S209, if some active bearer contexts related to the UE exist inthe old MME, the old MME needs to send a Delete Bearer Request to arelated gateway, and the related gateway may respond with a DeleteBearer Response, so that the old MME deletes the bearer contexts.

In Step S210, the HSS sends an Insert Subscriber Data message to the newMME. If the new MME verifies that the UE is allowed to attach, the newMME constructs a context for the UE, and returns an Insert SubscriberData Ack message to the HSS.

In Step S211, the HSS sends an Update Location Ack message to the newMME.

In Step S211 a, the new MME selects a suitable PDN GW according toinformation such as an APN or a Fully Qualified Domain Name (FQDN). ThePDN GW may be selected according to an APN-based policy and withreference to configuration of a user plane entity (UPE) pool, locationof the PDN GW, equipment load, operator subscription information,roaming protocol, and other information. The HSS may also provide a setof PDN GW addresses, and the new MME may directly select a suitable PDNGW according to the configuration of UPE pool, location of the PDN GW,equipment load, operator subscription information, roaming protocol, andother information. Definitely, this step is optional when the PDN GWaddresses may be directly provided by the HSS, for example, when the UEin the active state is handed over from a non-3GPP network to a 3GPPnetwork or when the UE is attached to the 3GPP network for the firsttime and the HSS only provides a unique PDN GW address to the MME.

In Step S212, the new MME sends a Create Default Bearer Request to theselected serving GW. The Create Default Bearer Request may contain theIMSI and a context identity of the new MME.

In Step S213, the serving GW creates a new entity in an evolved packetsystem (EPS) bearer table, and sends the Create Default Bearer Requestmessage to the PDN GW.

In Step S214, if a policy control and charging (PCC) system is appliedin the network, the PDN GW may need to interact with a policy chargingrule function (PCRF) to obtain a default PCC rule set for the UE.

In Step S215, the PDN GW returns a Create Default Bearer Responsemessage to the serving GW. If an address has been assigned to the PDNGW, the Create Default Bearer Response message may contain the addressof the PDN GW.

In Step S216, the serving GW returns the Create Default Bearer Responsemessage to the new MME.

In Step S216 a, if the UE has subscribed to mobility capability in anon-3GPP network, the new MME may register the address of the PDN GW anda corresponding APN with the HSS. Definitely, the new MME may alsoregister the address of the PDN GW with the HSS according to aconfiguration parameter thereof, so as to maintain the servicecontinuity when the UE is handed over between the 3GPP network and thenon-3GPP network. Specifically, after obtaining a set of PDN GWaddresses in Step S211 a, the new MME will select a suitable PDN GWaccording to the description in Step S211 a; and after a bearer issuccessfully established between the serving GW and the PDN GW, the newMME may register a flag of the address of the selected PDN GW with theHSS, so as to indicate that the PDN GW has been selected as a user PDNanchor point by the new MME.

As the HSS needs to provide PDN GW addresses to the new MME and recordthe registered PDN GW addresses, the HSS may be additionally providedwith the following subscription data.

PDN GW list (including Maintain a list of related PDN GW addresses PDNGW address provided to the UE and flags indicating and flag) whether aPDN GW is selected Register PDN GW address PDN GW address registeredwith the HSS

In Step S217, the new MME sends an Attach Accept message to the eNodeB.The Attach Accept message may contain a security context, quality ofservice (QoS), uplink tunnel information, the PDN GW address assigned tothe UE, and other information.

In Step S218, the eNodeB sends a Radio Bearer Establishment Request andan Attach Accept message to the UE. Definitely, the Attach Acceptmessage may be contained in the Radio Bearer Establishment Request, oron the contrary, the Radio Bearer Establishment Request may also becontained in the Attach Accept message.

In Step S219, the UE sends a Radio Bearer Establishment Response to theeNodeB. In addition, the UE may also send an Attach Complete message tothe eNodeB. Definitely, the Attach Accept message may be contained inthe Radio Bearer Establishment Response, or on the contrary, the RadioBearer Establishment Response may also be contained in the Attach Acceptmessage.

In Step S220, the eNodeB forwards an Attach Complete message to the newMME. The Attach Complete message may be contained in an S1-MME interfacecontrol message, and the control message also contains downlink tunnelinformation.

In Step S221, the new MME sends an Update Bearer Request message to theserving GW. The Update Bearer Request message may contain an eNodeBaddress and a downlink tunnel parameter.

In Step S222, the serving GW returns an Update Bearer Response messageto the new MME.

In the embodiment shown in FIG. 2A and FIG. 2B, if a plurality ofbearers needs to be established, different network entities may triggerthe establishment of different bearers, for example, pre-establishedvirtual private network (VPN) scenarios and dedicated signaling bearers.The network entities may include the MME, the serving GW, the PCRF, thePDN GW, and the like. Therefore, the PDN GW addresses selected forestablishing the new bearers also need to be registered with the HSS.Accordingly, the HSS needs to store PDN GW addresses of differentbearers, and different PDN GW addresses may be selected for differentbearers.

In addition, the HSS and an authentication, authorization, andaccounting (AAA) server may be implemented as an entity or separateentities. Likewise, the HSS and a subscription profile repository (SPR)may be implemented as an entity or separate entities.

Moreover, if the UE is attached to the non-3GPP network, the MME may beequivalent to an access gateway entity such as an ePDG or an accessserving network gateway (ASN GW), and the entity may register the PDN GWaddresses with the AAA server after the bearers are successfullyestablished.

In the embodiment shown in FIG. 2A and FIG. 2B, as the MME is a controlplane entity and has an interface with the HSS, the MME may register aselected PDN GW address with the HSS according to a parameter configuredon the MME when the UE selects a related PDN GW for the first time.

In the embodiment shown in FIG. 3A and FIG. 3B, a PCC system registersan address of a PDN GW with the HSS.

As shown in FIG. 3A and FIG. 3B, the process includes the followingsteps.

Steps S301-S311 are the same as Steps S201-S211 shown in FIG. 2.

In Step S311 a, the new MME selects a suitable PDN GW according toinformation such as an APN or an FQDN. The PDN GW may be selectedaccording to an APN-based policy and with reference to configuration ofthe UPE pool, location of the PDN GW, equipment load, operatorsubscription information, roaming protocol, and other information. TheHSS may also provide a set of PDN GW addresses, and the new MME maydirectly select a suitable PDN GW according to the configuration of theUPE pool, location of the PDN GW, equipment load, operator subscriptioninformation, roaming protocol, and other information. Definitely, thisstep is optional, for example, when the UE in the active state is handedover from a non-3GPP network to a 3GPP network or when the UE isattached to the 3GPP network for the first time and the HSS onlyprovides a unique PDN GW address to the new MME.

In addition, the new MME needs to determine whether to trigger a processfor registering the PDN GW address with the HSS/SPR through a PCC systemor not. A condition for the determination may be subscription data ofthe UE or a parameter configured on the new MME.

In Step S312, the new MME sends a Create Default Bearer Request to theserving GW. The Create Default Bearer Request may contain a parameterfor registering the PDN GW address with the HSS/SPR, and the parameterindicates that the PDN GW registers the selected PDN GW address with theHSS/SPR through the PCC system. The parameter is optional, that is, thePDN GW may directly configure related options to ensure that the PDN GWaddress is registered with the HSS/SPR/AAA server through the PCCsystem.

In Step S313, the serving GW sends the Create Default Bearer Requestmessage to the PDN GW. The Create Default Bearer Request may contain theparameter mentioned in Step S312 so as to trigger the PDN GW to registerthe address thereof with the HS S/SPR.

In Step S314, if the PCC system is applied in the network, the PDN GWmay need to interact with the PCRF to obtain a default PCC rule set forthe UE (here, scenarios of local breakout, that is, access to localservices are included). When the PDN GW is located in a roaming area,the PDN GW will interact with a home-PCRF (H-PCRF) through a visit-PCRF(V-PCRF).

A related attribute value pair (AVP) may be added into a messageinteracted between the PDN GW and the PCRF to trigger the PCRF toregister the PDN GW address with the HSS/SPR, which is specificallyimplemented as follows.

<CC-Request> ::= < Diameter Header: 272, REQ, PXY >  < Session-Id >  {Auth-Application-Id }  { Origin-Host }  { Origin-Realm }  {Destination-Realm }  { CC-Request-Type }  { CC-Request-Number }  [Destination-Host ]  [ Origin-State-Id ] *[ Subscription-Id ]  [Bearer-Control-Mode ]  [ Network-Request-Support ]  [ Bearer-Identifier]  [ Bearer-Operation ]  [ Framed-IP-Address ]  [ Framed-IPv6-Prefix ] [ 3GPP-RAT-Type ]  [ Termination-Cause ]  [ User-Equipment-Info ]  [3GPP-GPRS-Negotiated-QoS-Profile ]  [ 3GPP-SGSN-MCC-MNC ]  [3GPP-SGSN-Address ]  [ 3GPP-SGSN-IPv6-Address ]  [ Called-Station-ID ] [ Bearer-Usage ] *[ TFT-Packet-Filter-Information ] *[Charging-Rule-Report] *[ Event-Trigger]  [Access-Network-Charging-Address ] *[Access-Network-Charging-Identifier-Gx ] *[Flag of Register PCEF addressto HSS/SPR ] *[ Proxy-Info ] *[ Route-Record ] *[ AVP ]

In Step S314 a, the PCRF may initiate a process for obtaining thesubscription data of the UE from the HSS/SPR and then register the PDNGW address with the HSS/SPR. In addition, if the PCRF has thesubscription data of the UE, the PCRF may only initiate the process forregistering the PDN GW address with the HSS/SPR.

Steps S315-S322 may be the same as Steps S215-S222 shown in FIG. 2B,except that if the Create Default Bearer Request sent by the new MME tothe serving GW in Step S312 contains the parameter for registering thePDN GW address with the HSS/SPR, the Create Default Bearer Responsemessage in Steps S315 and S316 may contain a parameter indicating thatthe PDN GW address is successfully registered with the HSS/SPR.

In the embodiment shown in FIG. 3A and FIG. 3B, the process in the priorart may be adopted, and no additional message is introduced.

In addition, if the UE is attached to the non-3GPP network, the MME maybe equivalent to an access gateway entity such as an ePDG or an ASN GW;and the PDN GW may register the PDN GW addresses with the HSS/AAAserver/SPR through the PCC system after the bearers are successfullyestablished.

In the process shown in FIG. 3A and FIG. 3B, when the PDN GW address isregistered with the HSS/SPR, if the network supports multiple PDNs or aPDN GW is connected to multiple PDNs, APN information also needs to beregistered with the HSS/SPR together with the PDN GW. The HSS needs tostore a corresponding relation between the APN and the PDN GW.

In the embodiment shown in FIG. 4A and FIG. 4B, a PDN GW directlyregisters an address thereof with an HSS. The embodiment shown in FIG.4A and FIG. 4B may include local breakout scenarios.

As shown in FIG. 4A and FIG. 4B, the process includes the followingsteps.

Steps S401-S411 are the same as Steps S201-S211 shown in FIG. 2.

In Step S411 a, the new MME selects a suitable PDN GW according toinformation such as an APN or an FQDN. The PDN GW may be selectedaccording to an APN-based policy and with reference to configuration ofthe UPE pool, location of the PDN GW, equipment load, operatorsubscription information, roaming protocol, and other information. TheHSS may also provide a set of PDN GW addresses, and the new MME maydirectly select a suitable PDN GW according to the configuration of theUPE pool, location of the PDN GW, equipment load, operator subscriptioninformation, roaming protocol, and other information. Definitely, thisstep is optional, for example, when the UE in the active state is handedover from a non-3GPP network to a 3GPP network or when the UE isattached to the 3GPP network for the first time and the HSS onlyprovides a unique PDN GW address to the new MME.

In addition, the new MME needs to determine whether to trigger the PDNGW to register the address thereof with the HSS/SPR or not. A conditionfor the determination may be subscription data of the UE or a parameterconfigured on the new MME.

In Step S412, the new MME sends a Create Default Bearer Request to theserving GW. The Create Default Bearer Request may contain a parameterfor registering the PDN GW address with the HSS/SPR. The parameter isoptional, that is, the PDN GW may directly configure related optionparameters to ensure that the address thereof is directly registeredwith the HSS/SPR/AAA server.

In Step S413, the serving GW creates a new entity in an EPS bearertable, and transparently transmits the Create Default Bearer Requestsent by the new MME to the PDN GW.

In Step S414, the PDN GW registers the address thereof to the HSS/AAAserver, and the HSS/AAA server returns a related indication to the PDNGW.

Steps S415-S422 may be the same as Steps S215-S222 shown in FIG. 2,except that if the Create Default Bearer Request sent by the new MME tothe serving GW in Step S412 contains the parameter for registering thePDN GW address with the HSS/SPR, the Create Default Bearer Responsemessage in Steps S415 and S416 may contain a parameter indicating thatthe PDN GW address is successfully registered with the HSS/SPR.

In the embodiment shown in FIG. 4A and FIG. 4B, the process in the priorart may be adopted, and no additional message is introduced.

In addition, in the embodiment shown in FIG. 4A and FIG. 4B, if the HSSand the AAA server are separate entities, the PDN GW may register theaddress thereof with the AAA server, and then the AAA server transmitsthe address of the PDN GW to the HSS.

Moreover, if the UE is attached to the non-3GPP network, the MME may beequivalent to an access gateway entity such as an ePDG or an ASN GW; andthe PDN GW may directly register the addresses thereof with the HSS/AAAserver after the bearers are successfully established.

It should also be noted that, the network entity that triggers the PDGGW to register the addresses thereof with the HSS may be, but is notlimited to, the MME, the serving GW, the PDN GW, the ePDG, or the ASNGW.

In the process shown in FIG. 4A and FIG. 4B, when the PDN GW address isregistered with the HSS/SPR, if the network supports multiple PDNs or aPDN GW is connected to multiple PDNs, APN information also needs to beregistered with the HSS/SPR together with the PDN GW. The HSS needs tostore a corresponding relation between the APN and the PDN GW.

Embodiments shown in FIGS. 5, 6, and 7 respectively describe processesfor registering an address of a PDN GW with an HSS/SPR when a terminalinitiates a bearer establishment process in a 3GPP access network.

Specifically, in the embodiment shown in FIG. 5, if a UE initiates aservice from the 3GPP network to access an external PDN for the firsttime, the PDN GW directly registers the address thereof with the HSS.This embodiment includes local breakout scenarios.

As shown in FIG. 5, the process includes the following steps.

In Step S501, a UE sends an Active Packet Data Protocol (PDP) ContextRequest message to an SGSN.

In Step S502, the SGSN selects a related serving GW and PDN GW accordingto subscription data of the UE and APN information carried in the ActivePDP Context Request message, and determines whether the PDN GW isrequired to register an address thereof with an HSS or not. A conditionfor the determination may be subscription data of the UE. The processfor determining the condition is optional, for example, the PDN GW mayalso directly determine whether to register the address thereof with theHSS or not according to a parameter configured on the PDN GW.

In Step S503, the SGSN initiates a Create PDP Context Request message tothe serving GW. The Active PDP Context Request message may contain theaddress of the PDN GW and the APN information, and may also contain anindication indicating whether the PDN GW is required to register theaddress thereof with the HSS or not. It should be noted that, theindication is optional.

In Step S504, the serving GW initiates a Create System ArchitectureEvolution (SAE) Bearer Request to the PDN GW. The Active SAE BearerRequest may contain a registration indicator bit, an APN, and otherinformation.

In Step S504 a, the PDN GW requests a PCC rule from a V/H PCRF.

In Step S504 b, if the UE establishes a bearer to the PDN GW for thefirst time, the PDN GW directly registers the address thereof with theHSS. The PDN GW may determine whether to register the address thereofwith the HSS or not according to the registration indicator bit providedin the received Create SAE Bearer Request or a parameter configured onthe PDN GW.

Step S504 a and Step S504 b are performed in no particular order.

In Step S505, the PDN GW returns a Create SAE Bearer Response to theserving GW. The Create SAE Bearer Response may contain a parameterindicating that the PDN GW is successfully registered with the HSS.

In Step S506, the serving GW returns a Create PDP Context Response tothe SGSN. The Create PDP Context Response may contain a parameterindicating that the PDN GW is successfully registered to the HSS.

In Step S507, the SGSN returns an Active PDP Context Accept message tothe UE.

In Step S502, the PDG GW address may also be selected by the serving GW.In this scenario, the create bearer request message initiated by theSGSN to the serving GW only contains the APN or a set of PDN GWaddresses or one PDN GW address. The serving GW may select a PDG GWaccording to some conditions. In addition, a parameter may also be addedin Step S504 to indicate that the PDN GW registers the address thereofwith the HSS/AAA server.

In the embodiment shown in FIG. 6, if a UE establishes a bearer to a PDNGW in a 3GPP network for the first time, an SGSN registers an address ofthe PDN GW with an HSS. This embodiment includes local breakoutscenarios.

As shown in FIG. 6, the process includes the following steps.

In Step S601, a UE sends an Active PDP Context Request message to anSGSN.

In Step S602, the SGSN selects a related serving GW and PDN GW accordingto subscription data of the UE and APN information carried in the ActivePDP Context Request message.

In Step S603, the SGSN initiates a Create PDP Context Request message tothe serving GW. The Create PDP Context Request message may contain anaddress of the PDN GW and the APN information. The PDN GW may also beselected by the serving GW according to the APN information and otherconditions, for example, the SGSN may also provide a set of PDN GWaddresses, and the serving GW selects a PDN GW according to conditionssuch as load and network configuration.

In Step S604, the serving GW initiates a Create SAE Bearer Request tothe PDN GW. The Active SAE Bearer Request may contain the APNinformation or the address of the PDN GW.

In Step S604 a, the PDN GW may interact with a PCRF to obtain a PCCrule.

In Step S605, the PDN GW returns a Create SAE Bearer Response to theserving GW.

In Step S606, the serving GW returns a Create PDP Context Responsemessage to the SGSN. The message may contain the address of the PDN GWif the address is selected by the serving GW.

In Step S607, the SGSN may determine whether to register the address ofthe PDN GW with an HS S or not according to the subscription data of theUE, whether the UE has mobility in non-3GPP networks, or a parameterconfigured on the SGSN. The address of the PDN GW may be obtained by theSGSN by querying the APN information, or be provided by the serving GWin Step S606.

In Step S608, the SGSN returns an Active PDP Context Accept message tothe UE.

In the process shown in FIG. 6, when the PDN GW address is registeredwith the HSS/SPR, if the network supports multiple PDNs or a PDN GW isconnected to multiple PDNs, APN information also needs to be registeredwith the HSS/SPR together with the PDN GW. The HSS needs to store acorresponding relation between the APN and the PDN GW.

In the embodiment shown in FIG. 7, if a UE initiates a service in a 3GPPnetwork to establish a bearer to an external PDN for the first time, anaddress of a PDN GW is registered with an HSS/AAA server/SPR through aPCC system. This embodiment includes local breakout scenarios.

In Step S701, a UE sends an Active PDP Context Request message to anSGSN.

In Step S702, the SGSN selects a related serving GW and PDN GW accordingto APN information, and determines whether to trigger a process forregistering an address of the PDN GW with an HSS/SPR through a PCCsystem or not. A condition for the determination may be subscriptiondata of the UE or a parameter configured on the SGSN. In addition, theSGSN may also not perform such a determination process, but directlydetermines whether to register the address of the PDN GW with theHSS/SPR through the PCC system or not according to a configurationparameter on the PDN GW.

As for the selection of the serving GW and PDN GW, the following shouldbe noted.

A. The SGSN may select a serving GW and a PDN GW according to APNinformation, a parameter configured on the SGSN, or subscription data ofthe UE through DNS query, for example, select a serving GW and a PDN GWthrough two DNS queries. In addition, the SGSN provides informationabout the address of the PDN GW to the serving GW.

B. The serving GW may select a PDN GW according to a parameterconfigured on the serving GW or subscription data of the UE through DNSquery. For example, the SGSN may provide APN information to the servingGW, and the serving GW queries a DNS system to obtain information aboutthe PDN GW.

C. The HSS directly provides the information about the PDN GW to theSGSN. If the HSS provides a set of IP addresses or FQDNs, a PDN GW maybe selected by the SGSN according to information such as an APN, or beselected by the serving GW according to the APN information and aparameter configured on the serving GW.

In Step S703, the SGSN initiates an Active PDP Context Request messageto the serving GW. The Active PDP Context Request message contains aparameter for registering the address of the PDN GW with the HSS/SPR, soas to indicate that the address of the PDN GW is registered with theHSS/SPR through the PCC system. Definitely, the parameter is optional.The PDN GW may also be selected by the serving GW according toinformation such as the APN.

In Step S704, the serving GW initiates an Active SAE Bearer Request tothe PDN GW. The Active SAE Bearer Request may contain a registrationindicator bit, the APN information, and other parameters. Definitely,the serving GW may also trigger an indication to the PDN GW indicatingthat the address of the PDN GW is registered with the HS S/AAAserver/SPR through the PCC system.

In Step S704 a, PCRF interaction is involved. Here, local breakoutscenarios are included. When the PDN GW is located in a roaming area,the PDN GW may interact with an H-PCRF through a V-PCRF.

A related AVP may be added into a credit control request (CCR) messageinteracted between the PDN GW and the PCRF to trigger the PCRF toregister the address of the PDN GW with the HSS/SPR.

In Step S704 b, the PCRF may initiate a process for obtaining thesubscription data of the UE from the HSS/SPR and then register theaddress of the PDN GW with the HSS/SPR. If the PCRF has the subscriptiondata of the UE, the PCRF only initiates the process for registering theaddress of the PDN GW with the HSS/SPR.

In Step S705, the PDN GW returns an Active SAE Bearer Response to theserving GW. The response message may contain a parameter identifierindicating a successful registration.

In Step S706, the serving GW returns an Active PDP Context Response tothe SGSN. The response message may contain a parameter identifierindicating a successful registration.

In Step S707, the SGSN returns an Active PDP Context Accept message tothe UE.

Embodiments shown in FIGS. 8, 9, and 10 respectively describe processesfor registering an address of a PDN GW with an HSS/SPR when a terminalinitiates a bearer establishment process in an SAE/Long Term Evolution(LTE) access network.

Specifically, in the embodiment shown in FIG. 8, if a UE initiates theestablishment of a service from an SAE/LTE network to an external PDNfor the first time, an MME registers an address of a PDN GW with an HSS.This embodiment includes local breakout scenarios.

In the process shown in FIG. 8, when the PDN GW address is registeredwith the HSS/SPR, if the network supports multiple PDNs or a PDN GW isconnected to multiple PDNs, APN information also needs to be registeredwith the HSS/SPR together with the PDN GW. The HSS needs to store acorresponding relation between the APN and the PDN GW.

As shown in FIG. 8, the process includes the following steps.

In Step S801, a UE initiates an Active SAE Bearer Request. In Step S802,a new MME selects a PDN GW. Here, multiple PDN scenarios are included.

When selecting the PDN GW, the MME may obtain the PDN GW according to anindication carried by the UE such as APN information, or determine anaddress of the PDN GW according to a parameter provided by an HSSthrough the default configuration in the HSS.

In Steps S803-S806, a bearer establishment process at the core networkis performed.

In Step S807, the new MME initiates a process for registering theaddress of the PDN GW with the HSS. In addition, before initiating theregistration process, the new MME may determine whether to initiate theregistration process or not according to subscription data of the UE,capability of the UE, or a parameter configured on the new MME.

In Step S808, the new MME returns an Active SAE Bearer Response to aneNodeB. The Active SAE Bearer Response may contain a configurationparameter at the related radio side and configuration information ofrelated uplink tunnels. The message contains a parameter forestablishing an air interface radio bearer. The eNodeB will establish arelated radio bearer according to the provided parameter forestablishing a radio bearer.

In Steps S809-S810, a radio bearer establishment process is performed.

In Step S811, the eNodeB initiates an Update Bearer Request to the newMME. The Update Bearer Request may contain information about relateddownlink tunnels between the eNodeB and the serving GW.

In Step S812, after radio air interface resources are successfullyestablished, the eNodeB returns an Active SAE Bearer Response to the UE.

In Step S813, the new MME initiates an Update Bearer Request to theserving GW. The Update Bearer Request may contain the information aboutthe related downlink tunnels between the eNodeB and the serving GW.

In Step S814, the serving GW returns an Update Bearer Response to thenew MME.

The embodiment shown in FIG. 8 may include the following scenario, i.e.,after the UE is attached to the SAE/LTE network, the UE initiates apreconfigured bearer establishment process immediately, for example, inscenarios such as a preconfigured VPN.

In addition, the embodiment shown in FIG. 8 may include scenarios wherethe UE initiates a service in a non-3GPP network, for example, multiplePDN and multiple home agent (HA) scenarios. As such, the MME isequivalent to a control-plane access gateway entity such as an ePDG oran ASN GW; and the entity such as the ePDG or the ASN GW may directlyregister the address of the PDN GW with the HSS/AAA server/SPR after thebearers are successfully established. If the AAA server and the HSS areseparate entities, the registered PDN GW address may be transmitted bythe AAA server to the HSS.

In the process shown in FIG. 8, when the PDN GW address is registeredwith the HSS/SPR, if the network supports multiple PDNs or a PDN GW isconnected to multiple PDNs, APN information also needs to be registeredwith the HSS/SPR together with the PDN GW. The HSS needs to store acorresponding relation between the APN and the PDN GW.

In the embodiment shown in FIG. 9, if a UE initiates the establishmentof a service from an SAE/LTE access network to an external PDN for thefirst time, an address of a PDN GW is registered with an HSS through aPCC system. This embodiment includes local breakout scenarios.

As shown in FIG. 9, the process includes the following steps.

In Step S901, a UE initiates an Active SAE Bearer Request.

In Step S902, a new MME selects a PDN GW.

In Step S903, the new MME initiates a Create SAE Bearer Request to aserving GW. The Active SAE Bearer Request may contain an address of theselected PDN GW.

In Step S904, the serving GW initiates a Create SAE Bearer Request tothe PDN GW. The Active SAE Bearer Request may contain an address of theselected PDN GW.

In Step S905, the PDN GW may interact with a PCRF to obtain a defaultPCC rule set for the UE. When the PDN GW is located in a roaming area,the PDN GW will interact with an H-PCRF through a V-PCRF.

In Step S905 a, the PCRF may initiate a process for obtainingsubscription data of the UE from the HSS/SPR and then register the PDNGW address with the HSS/AAA server/SPR. In addition, if the PCRF has thesubscription data of the UE, the PCRF may only initiate the process forregistering the PDN GW address with the HSS/SPR.

In Step S906, the PDN GW returns an Active SAE Bearer Response to theserving GW. The Active SAE Bearer Response may contain QoS information.

In Step S907, the serving GW returns an Active SAE Bearer Response tothe new MME. The Active SAE Bearer Response may contain QoS information.

In Step S908, the new MME returns an Active SAE Bearer Response to theUE, and performs a radio bearer configuration (configuration RB)process.

In Step S909, the new MME returns an Active SAE Bearer Response to aneNodeB.

In Step S910, the eNodeB initiates a Radio Bearer Establishment Requestto the UE.

In Step S911, the UE returns a Radio Bearer Establishment Response tothe eNodeB.

In Step S912, the eNodeB initiates an Update Bearer Request to the newMME.

In Step S913, the eNodeB returns an Active SAE Bearer Response to theUE.

In Step S914, the new MME initiates an Update Bearer Request to theserving GW.

In Step S915, the serving GW returns an Update Bearer Response to thenew MME.

The embodiment shown in FIG. 9 may include scenarios where the UEinitiates a service in a non-3GPP network, for example, multiple PDN andmultiple HA scenarios. As such, the MME is equivalent to a control-planeaccess gateway entity such as an ePDG or an ASN GW; and the PDN GW mayregister the address of the PDN GW with the HSS/AAA server/SPR throughthe PCC system after the bearers are successfully established. If theAAA server and the HSS are separate entities, the registered PDN GWaddress may be transmitted by the AAA server to the HSS.

In the process shown in FIG. 9, when the PDN GW address is registeredwith the HSS/SPR, if the network supports multiple PDNs or a PDN GW isconnected to multiple PDNs, APN information also needs to be registeredwith the HSS/SPR together with the PDN GW. The HSS needs to store acorresponding relation between the APN and the PDN GW.

It should also be noted that, the entity and conditions for triggeringthe PCRF to register the PDN GW address with the HSS/SPR when the PDN GWinteracts with the PCRF have been mentioned in the foregoingembodiments, so the details will not be described herein again.

In the embodiment shown in FIG. 10, if a UE initiates the establishmentof a service from an SAE/LTE access network to an external PDN for thefirst time, a PDN GW directly registers an address thereof with an HSS.This embodiment includes local breakout scenarios.

In Step S1001, a UE initiates an Active SAE Bearer Request.

In Step S1002, a new MME selects a PDN GW.

In Step S1003, the new MME initiates an Active SAE Bearer Request to aserving GW. The Active SAE Bearer Request may contain an address of theselected PDN GW.

In Step S1004, the serving GW initiates an Active SAE Bearer Request tothe PDN GW. The Active SAE Bearer Request may contain an address of theselected PDN GW.

In Step S1005, the PDN GW may interact with a PCRF to obtain a defaultPCC rule set for the UE.

In Step S1005 a, if the UE establishes a bearer to the PDN GW for thefirst time, the PDN GW directly registers the address thereof with theHSS/SPR.

In Step S1006, the PDN GW returns an Active SAE Bearer Response to theserving GW. The Active SAE Bearer Response may contain QoS information.

In Step S1007, the serving GW returns an Active SAE Bearer Response tothe new MME. The Active SAE Bearer Response may contain QoS information.

In Step S1008, the new MME returns an Active SAE Bearer Response to theUE, and performs a radio bearer configuration process.

In Step S1009, the new MME returns an Active SAE Bearer Response to aneNodeB.

In Step S1010, the eNodeB initiates a Radio Bearer Establishment Requestto the UE.

In Step S1011, the UE returns a Radio Bearer Establishment Response tothe eNodeB.

In Step S1012, the eNodeB initiates an Update Bearer Request to the newMME.

In Step S1013, the eNodeB returns an Active SAE Bearer Response to theUE.

In Step S1014, the new MME initiates an Update Bearer Request to theserving GW.

In Step S1015, the serving GW returns an Update Bearer Response to thenew MME.

The embodiment shown in FIG. 10 may include scenarios where the UEinitiates a service in a non-3GPP network, for example, multiple PDN andmultiple HA scenarios. As such, the MME is equivalent to a control-planeaccess gateway entity such as an ePDG or an ASN GW; and the PDN GW maydirectly register the address thereof with the HSS/AAA server/SPR afterthe bearers are successfully established. If the AAA server and the HSSare separate entities, the registered PDN GW address may be transmittedby the AAA server to the HSS.

It should also be noted that, the entity and conditions for triggeringthe PCRF to register the PDN GW address with the HSS/SPR when the PDN GWinteracts with the PCRF have been mentioned in the foregoingembodiments, so the details will not be described herein again.

In the process shown in FIG. 10, when the PDN GW address is registeredwith the HSS/SPR, if the network supports multiple PDNs or a PDN GW isconnected to multiple PDNs, APN information also needs to be registeredwith the HSS/SPR together with the PDN GW. The HSS needs to store acorresponding relation between the APN and the PDN GW.

As some of the above embodiments are applicable to a communicationsystem, the present disclosure further provides embodiments of thecommunication system.

Consistent with an embodiment, the present disclosure provides acommunication system. The communication system includes a bearer contextassignment entity and an address registration entity. The bearer contextassignment entity is configured to enable a network anchor point toassign a first bearer context to a terminal. The address registrationentity is configured to register an address of the network anchor pointwith a network server.

Consistent with an embodiment, the present disclosure provides acommunication system. The communication system includes a connectionestablishment entity and an address registration entity. The connectionestablishment entity is configured to establish a first connectionbetween a network anchor point and a terminal. The address registrationentity is configured to register an address of the network anchor pointwith a network server.

In the communication system according to the above embodiments, theaddress registration entity is further configured to register an APNcorresponding to the network anchor point with the network server whenan access network supports a plurality of PDNs or the network anchorpoint corresponds to a plurality of PDNs.

The address registration entity is an MME, or an SGSN, or an accessnetwork entity, or the network anchor point, or an entity in a PCCsystem.

As for the process for storing an address of a network anchor point to anetwork server by using the communication system, reference may be madeto the descriptions in the above method embodiments.

In actual applications, a current service of the terminal may need to beterminated. Accordingly, an address of a PDN GW stored in an HSS mayalso be deleted. Therefore, the present disclosure further provides amethod for deleting an address of a network anchor point from a networkserver.

In order to enable those skilled in the art to easily delete an addressof a network anchor point from a network server, several embodiments areintroduced below with reference to the accompanying drawings.

Embodiments as shown in FIGS. 11, 12, and 13 respectively describeprocesses for deleting an address of a PDN GW from an HSS when aterminal initiates a bearer deletion process in an SAE/LTE accessnetwork.

Specifically, in the embodiment shown in FIG. 11, when all bearersrelated to a UE on a PDN GW are released, a PCC system deletes anaddress of the PDN GW stored in an HSS/SPR.

As shown in FIG. 11, the process includes the following steps.

In Step S1101, a UE initiates a Deactive SAE Bearer Request.

In Step S1102, a new MME initiates the Deactive SAE Bearer Request to aserving GW. The Deactive SAE Bearer Request may contain informationindicating the PDN GW that the address of the PDN GW in the HSS/SPR isderegistered through a PCC system.

In Step S1103, the serving GW initiates a Deactive SAE Bearer Request tothe PDN GW. The Deactive SAE Bearer Request may contain informationindicating the PDN GW that the address of the PDN GW in the HSS/SPR isderegistered through the PCC system. The message that triggers thederegistration of the PDN GW may be provided by the MME or the servingGW, and the PDN GW may also determine to initiate the process forderegistering the PDN GW address through the PCC system according tonetwork configuration.

In Step S1104, the PDN GW interacts with a PCRF to release relatedbinding information.

In Step S1104 a, the PCRF deregisters the PDN GW address stored in theHSS/SPR (deregister PDN GW to HSS). Before the deregistration, the PDNGW may determine whether the PDN GW address stored in the HSS/SPR needsto be deregistered through the PCC system or not according to thereceived indication information or according to a parameter configuredon the PDN GW. If the network allows a terminal to use multiple PDNs,the HSS may have stored a corresponding relation between the PDN GW andan APN; and at this time, the deregistration process of the PDN GWfurther includes deleting the corresponding relation between the PDN GWaddress and the APN stored in the HSS/SPR.

In Step S1105, the PDN GW returns a Deactive SAE Bearer Response to theserving GW. If the Deactive SAE Bearer Request in Step S1102 contains anindication, the Deactive SAE Bearer Response may also contain asuccessful deregistration indication.

In Step S1106, the serving GW returns a Deactive SAE Bearer Response tothe new MME. The message may contain a successful deregistrationindication.

In Step S1107, the new MME returns a Deactive SAE Bearer Response to theUE.

The embodiment shown in FIG. 11 may include scenarios where the UEterminates a service in a non-3GPP network, for example, multiple PDNand multiple HA scenarios. When all services related to the UE on thePDN GW are terminated, the PDN GW may deregister the PDN GW address fromthe HSS/AAA server/SPR through the PCC system. If the AAA server and theHSS are separate entities, the deregistration parameter or informationmay be transmitted by the AAA server to the HSS.

In the embodiment shown in FIG. 12, when all bearers related to a UE ona PDN GW are released, the PDN GW directly deletes an address thereofstored in an HSS/SPR.

As shown in FIG. 12, the process includes the following steps.

In Step S1201, a UE initiates a Deactive SAE Bearer Request.

In Step S1202, a new MME initiates a Deactive SAE Bearer Request to aserving GW. The Deactive SAE Bearer Request may contain informationindicating that the PDN GW directly deregisters the address thereof inthe HSS/SPR.

In Step S1203, the serving GW initiates a Deactive SAE Bearer Request tothe PDN GW. The Deactive SAE Bearer Request may contain informationindicating that the PDN GW directly deregisters the address thereof inthe HSS/SPR. The message that triggers the deregistration of the PDN GWmay be provided by the MME or the serving GW, and the PDN GW may alsodetermine to initiate the process for deregistering the address from theHSS/AAA server according to network configuration.

In Step S1204, the PDN GW interacts with a PCRF to release relatedbinding information. This step is optional, and includes local breakoutscenarios, that is, the PDN GW interacts with an H-PCRF through aV-PCRF.

In Step S1204 a, the PDN GW directly deregisters the address thereof inthe HSS/SPR (deregister PDN GW to HSS). Before the deregistration, thePDN GW may determine whether to directly deregister the address thereofin the HSS/SPR or not according to the received indication informationor a parameter configured on the PDN GW.

In Step S1205, the PDN GW returns a Deactive SAE Bearer Response to theserving GW. If the Deactive SAE Bearer Request in Step S1202 contains anindication, the Deactive SAE Bearer Response may also contain asuccessful deregistration indication.

In Step S1206, the serving GW returns a Deactive SAE Bearer Response tothe new MME. The message may contain a successful deregistrationindication.

In Step S1207, the new MME returns a Deactive SAE Bearer Response to theUE.

The embodiment shown in FIG. 12 may include scenarios where the UEterminates a service in a non-3GPP network, for example, multiple PDNand multiple HA scenarios. When all services related to the UE on thePDN GW are terminated, the PDN GW may directly deregister the addressthereof from the HSS/AAA server/SPR. If the AAA server and the HSS areseparate entities, the deregistration parameter or information may betransmitted by the AAA server to the HSS.

If the network allows a terminal to use multiple PDNs, the HSS may havestored a corresponding relation between the PDN GW and an APN; and atthis time, the deregistration process of the PDN GW further includesdeleting the corresponding relation between the PDN GW address and theAPN stored in the HSS/SPR.

In the embodiment shown in FIG. 13, when all bearers related to a UE ona PDN GW are released, an MME deletes an address of the PDN GW stored inan HSS/SPR.

As shown in FIG. 13, the process includes the following steps.

In Step S1301, a UE initiates a Deactive SAE Bearer Request.

In Step S1302, a new MME initiates a Deactive SAE Bearer Request to aserving GW.

In Step S1303, the serving GW initiates a Deactive SAE Bearer Request tothe PDN GW.

In Step S1304, the PDN GW interacts with a PCRF to release relatedbinding information. This step is optional, and includes local breakoutscenarios, that is, the PDN GW interacts with an H-PCRF through aV-PCRF.

In Step S1305, the PDN GW returns a Deactive SAE Bearer Response to theserving GW.

In Step S1306, the serving GW returns a Deactive SAE Bearer Response tothe new MME.

In Step S1306 a, the new MME deregisters the PDN GW address in theHSS/SPR. Before the deregistration, the new MME may determine whether toderegister the PDN GW address in the HSS/SPR or not according tosubscription data of the UE or a parameter configured on the new MME.

In Step S1307, the new MME returns a Deactive SAE Bearer Response to theUE.

The embodiment shown in FIG. 13 may include scenarios where the UEterminates a service in a non-3GPP network, for example, multiple PDNand multiple HA scenarios. When all services related to the UE on thePDN GW are terminated, an entity such as an ePDG or an ASN GW that isequivalent to the MME may deregister the PDN GW address from HSS/AAAserver/SPR. If the AAA server and the HSS are separate entities, thederegistration parameter or information may be transmitted by the AAAserver to the HSS.

If the network allows a terminal to use multiple PDNs, the HSS may havestored a corresponding relation between the PDN GW and an APN; and atthis time, the deregistration process of the PDN GW further includesdeleting the corresponding relation between the PDN GW address and theAPN stored in the HSS/SPR.

Embodiments shown in FIGS. 14, 15, and 16 respectively describeprocesses for deleting an address of a PDN GW from an HSS when an MMEinitiates a bearer deletion process.

Specifically, in the embodiment shown in FIG. 14, when all bearersrelated to a UE on a PDN GW are released, the PDN GW directly deletes anaddress thereof stored in an HSS/SPR.

As shown in FIG. 14, the process includes the following steps.

In Step S1401, a new MME initiates a Deactive SAE Bearer Request to aserving GW. The Deactive SAE Bearer Request may contain informationindicating that a PDN GW deregisters a PDN GW address in an HSS. The newMME may determine whether to send the indication to the serving GW ornot according to subscription data of the UE or a parameter configuredon the new MME.

In Step S1402, the serving GW initiates a Deactive SAE Bearer Request tothe PDN GW.

In Step S1403, the PDN GW interacts with a PCRF to release relatedbinding information. This step is optional, and includes local breakoutscenarios, that is, the PDN GW interacts with an H-PCRF through aV-PCRF.

In Step S1404, the PDN GW directly deregisters the address thereofstored in the HSS/SPR. Before the deregistration, the PDN GW maydetermine whether to deregister the address thereof stored in theHSS/SPR or not according to the received indication information or aparameter configured on the PDN GW. The message that triggers thederegistration of the PDN GW may be provided by the MME or the servingGW, and the PDN GW may also determine to initiate the process forderegistering the address from the HSS/AAA server according to networkconfiguration.

In Step S1405, the PDN GW returns a Deactive SAE Bearer Response to theserving GW. If the Deactive SAE Bearer Request in Step S1401 contains anexplicit indication, the Deactive SAE Bearer Response may also contain asuccessful deregistration indication.

In Step S1406, the serving GW returns a Deactive SAE Bearer Response tothe new MME. The message may contain a successful deregistrationindication.

In Step S1407, the new MME initiates a Deactive SAE Bearer Request tothe UE. In addition, the new MME may also indicate an eNodeB to releasea related radio bearer. Definitely, the indication may also be sentafter Step S1401.

In Step S1408, the UE returns a Deactive SAE Bearer Response to the newMME.

The embodiment shown in FIG. 14 may include scenarios where the UEterminates a service in a non-3GPP network, for example, multiple PDNand multiple HA scenarios, and may also include scenarios where anentity such as an ePDG or an ASN GW initiates a bearer deletion process.When all services related to the UE on the PDN GW are terminated, thePDN GW may directly deregister the address thereof from the HSS/AAAserver/SPR. If the AAA server and the HSS are separate entities, thederegistration parameter or information needs to be transmitted by theAAA server to the HSS.

If the network allows a terminal to use multiple PDNs, the HSS may havestored a corresponding relation between the PDN GW and an APN; and atthis time, the deregistration process of the PDN GW further includesdeleting the corresponding relation between the PDN GW address and theAPN stored in the HSS/SPR.

In the embodiment shown in FIG. 15, when all bearers related to a UE ona PDN GW are released, an MME deletes an address of the PDN GW stored inan HSS/AAA server/SPR.

As shown in FIG. 15, the process includes the following steps.

In Step S1501, a new MME initiates a Deactive SAE Bearer Request to aserving GW.

In Step S1502, the serving GW initiates a Deactive SAE Bearer Request toa PDN GW.

In Step S1503, the PDN GW interacts with a PCRF to release relatedbinding information. This step is optional, and includes local breakoutscenarios, that is, the PDN GW interacts with an H-PCRF through aV-PCRF.

In Step S1504, the PDN GW returns a Deactive SAE Bearer Response to theserving GW.

In Step S1505, the serving GW returns the Deactive SAE Bearer Responseto the new MME.

In Step S1506, the new MME deregisters the PDN GW address in theHSS/SPR. Before the deregistration, the new MME may determine whether toderegister the PDN GW address from the HSS/SPR or not according tosubscription data of the UE or a parameter configured on the new MME.

In Step S1507, the new MME initiates a Deactive SAE Bearer Request tothe UE. In addition, the new MME may also indicate an eNodeB to releasea related radio bearer. Definitely, the indication may also be sentafter Step S1501.

In Step S1508, the UE returns a Deactive SAE Bearer Response to the newMME.

If the network allows a terminal to use multiple PDNs, the HSS may havestored a corresponding relation between the PDN GW and an APN; and atthis time, the deregistration process of the PDN GW further includesdeleting the corresponding relation between the PDN GW address and theAPN stored in the HSS/SPR.

The embodiment shown in FIG. 15 may include scenarios where the UEterminates a service in a non-3GPP network, for example, multiple PDNand multiple HA scenarios, and may also include scenarios where anentity such as an ePDG or an ASN GW initiates a bearer deletion process.When all services related to the UE on the PDN GW are terminated, theentity such as the ePDG or the ASN GW that is equivalent to the MME mayderegister the PDN GW address from the HSS/AAA server/SPR. If the AAAserver and the HSS are separate entities, the deregistration parameteror information needs to be transmitted by the AAA server to the HSS.

On the contrary, when the PDN GW address is registered with the HSS/AAAserver, if the AAA server and the HSS are separate entities, the PDN GWaddress needs to be transmitted by the AAA server to the HSS.

In the embodiment shown in FIG. 16, when all bearers related to a UE ona PDN GW are released, a PCC system deletes an address of the PDN GWstored in an HSS/SPR.

As shown in FIG. 16, the process includes the following steps.

In Step S1601, a new MME initiates a Deactive SAE Bearer Request to aserving GW. The Deactive SAE Bearer Request may contain informationindicating that a PDN GW deregisters a PDN GW address in an HSS/SPR byinteracting with a PCC system. The new MME may also determine whether tosend the indication to the serving GW according to subscription data ofthe UE or a parameter configured on the new MME.

In Step S1602, the serving GW initiates a Deactive SAE Bearer Request tothe PDN GW.

In Step S1603, the PDN GW interacts with the PCRF to release relatedbinding information. This step is optional, and includes local breakoutscenarios, that is, the PDN GW interacts with an H-PCRF through aV-PCRF. In addition, the PDN GW may also determine whether to triggerthe PCC system to deregister the PDN GW address in the HSS/SPR or notaccording to the received indication information or a parameterconfigured on the PDN GW.

In Step S1604, the PCRF interacts with the HSS/SPR to deregister the PDNGW address in the HSS/SPR.

In Step S1605, the PDN GW returns a Deactive SAE Bearer Response to theserving GW. If the Deactive SAE Bearer Request in Step S1601 contains anexplicit indication, the Deactive SAE Bearer Response may also contain asuccessful deregistration indication.

In Step S1606, the serving GW returns a Deactive SAE Bearer Response tothe new MME.

In Step S1607, the new MME initiates a Deactive SAE Bearer Request tothe UE. In addition, the new MME may also indicate an eNodeB to releasea related radio bearer. Definitely, the indication may also be sentafter Step S1601.

In Step S1608, the UE returns a Deactive SAE Bearer Response to the newMME.

If the network allows a terminal to use multiple PDNs, the HSS may havestored a corresponding relation between the PDN GW and an APN; and atthis time, the deregistration process of the PDN GW further includesdeleting the corresponding relation between the PDN GW address and theAPN stored in the HSS/SPR.

The embodiment shown in FIG. 16 may include scenarios where the UEterminates a service in a non-3GPP network, for example, multiple PDNand multiple HA scenarios, and may also include scenarios where anentity such as an ePDG or an ASN GW initiates a bearer deletion process.When all services related to the UE on the PDN GW are terminated, thePDN GW may deregister the PDN GW address from the HSS/AAA server/SPR viathe PCC. If the AAA server and the HSS are separate entities, thederegistration parameter or information needs to be transmitted by theAAA server to the HSS.

The entity and conditions for triggering the deregistration of the PDNGW address from the HSS/AAA server/SPR have been described in theforegoing embodiments, so the details will not be described hereinagain.

Embodiments shown in FIGS. 17, 18, and 19 respectively describeprocesses for deleting an address of a PDN GW from an HS S when anetwork initiates a bearer deletion process in an SAE/LTE accessnetwork.

Specifically, in the embodiment shown in FIG. 17, when all bearersrelated to a UE on a PDN GW are released, the PDN GW directly deletes anaddress thereof stored in an HSS/SPR.

As shown in FIG. 17, the process includes the following steps.

In Step S1701, a PCRF provides a PCC decision to a PDN GW (PCC DecisionProvision).

In Step S1702, the PDN GW triggers a bearer deletion process accordingto the received PCC decision. In this step, the PDN GW initiates aDeactive SAE Bearer Request to a serving GW.

In Step S1703, the serving GW initiates a Deactive SAE Bearer Request toan MME.

In Step S1704, the MME initiates a Deactive Bearer Request to an eNodeB.

In Step S1705, the eNodeB initiates a Deactive Radio Bearer Request to aUE.

In Step S1706, the UE removes a related uplink data stream template, andreturns a Deactive Radio Bearer Response to the eNodeB.

In Step S1707, the eNodeB returns a Deactive Bearer Response to the MME.

In Step S1708, the MME returns a Deactive SAE Bearer Response to theserving GW.

In Step S1709, the serving GW returns a Deactive SAE Bearer Response tothe PDN GW.

In Step S1710, the PDN GW returns a PCC Provision Ack to the PCRF.

In Step S1711, the PDN GW directly deregisters an address thereof storedin an HSS/SPR. Before the deregistration, the PDN GW may determinewhether to deregister the address thereof from the HSS or not accordingto subscription data of the UE or a parameter configured on the PDN GW.In addition, the PDN GW may also determine whether to deregister theaddress thereof from the HSS or not according to a request or anindication of the MME. As such, the MME may determine whether the PDN GWneeds to deregister the address thereof from the HSS or not according tothe subscription data of the UE or a parameter configured on the MME.

In addition, the serving GW may also provide an indication, and the PDNGW deregisters address information of the PDN GW from the HS S/AAAserver according to the indication provided by the serving GW.

If the network allows a terminal to use multiple PDNs, the HSS may havestored a corresponding relation between the PDN GW and an APN; and atthis time, the deregistration process of the PDN GW further includesdeleting the corresponding relation between the PDN GW address and theAPN stored in the HSS/SPR.

The embodiment shown in FIG. 17 may include scenarios where the UEterminates a service in a non-3GPP network, for example, multiple PDNand multiple HA scenarios, and may also include scenarios where the PDNGW initiates a bearer deletion process. When all services related to theUE on the PDN GW are terminated, the PDN GW may directly deregister theaddress thereof from the HSS/AAA server/SPR. If the AAA server and theHSS are separate entities, the deregistration parameter or informationneeds to be transmitted by the AAA server to the HSS.

In the embodiment shown in FIG. 18, when all bearers related to a UE ona PDN GW are released, a PCC system deletes an address of the PDN GWstored in an HSS/SPR.

As shown in FIG. 18, the process includes the following steps.

In Step S1801, a PCRF provides a PCC decision to a PDN GW.

In Step S1802, the PDN GW triggers a bearer deletion process accordingto the received PCC decision. In this step, the PDN GW initiates aDeactive SAE Bearer Request to a serving GW.

In Step S1803, the serving GW initiates a Deactive SAE Bearer Request toan MME.

In Step S1804, the MME initiates a Deactive Bearer Request to an eNodeB.

In Step S1805, the eNodeB initiates a Deactive Radio Bearer Request to aUE.

In Step S1806, the UE removes a related uplink data stream template, andreturns a Deactive Radio Bearer Response to the eNodeB.

In Step S1807, the eNodeB returns a Deactive Bearer Response to the MME.

In Step S1808, the MME returns a Deactive SAE Bearer Response to theserving GW.

In Step S1809, the serving GW returns a Deactive SAE Bearer Response tothe PDN GW.

In Step S1810, the PDN GW returns a PCC Provision Ack to the PCRF, andtriggers the PCRF to deregister an address of the PDN GW from anHSS/SPR.

In Step S1810 a, the PCRF deregisters the address of the PDN GW from theHSS/SPR.

In Step S1810, the PDN GW may trigger the PCRF to deregister the addressaccording to a parameter configured on the PDN GW or the Deactive SAEBearer Response returned by the MME in Step S1808. Likewise, the MME maydetermine whether to deregister the PDN GW address from the HSS/SPR byinteracting with a PCC system or not according to subscription data ofthe UE and a parameter configured on the MME.

Likewise, the serving GW may determine whether to deregister the PDN GWaddress from the HSS/SPR by interacting with a PCC system according toconditions such as a parameter configured on the serving GW, and providea related indication to the PDN GW to indicate that the PDN GW addressis deregistered through the PCC system.

If the network allows a terminal to use multiple PDNs, the HSS may havestored a corresponding relation between the PDN GW and an APN; and atthis time, the deregistration process of the PDN GW further includesdeleting the corresponding relation between the PDN GW address and theAPN stored in the HSS/SPR.

In addition, the embodiment shown in FIG. 18 may include scenarios wherethe UE terminates a service in a non-3GPP network, for example, multiplePDN and multiple HA scenarios, and may also include scenarios where thePDN GW initiates a bearer deletion process. When all services related tothe UE on the PDN GW are terminated, the PDN GW may deregister the PDNGW address from the HSS/AAA server/SPR through the PCC system. If theAAA server and the HSS are separate entities, the deregistrationparameter or information needs to be transmitted by the AAA server tothe HSS.

In the embodiment shown in FIG. 19, when all bearers related to a UE ona PDN GW are released, an MME deletes an address of the PDN GW stored inan HSS/SPR.

As shown in FIG. 19, the process includes the following steps.

In Step S1901, a PCRF provides a PCC decision to a PDN GW.

In Step S1902, the PDN GW triggers a bearer deletion process accordingto the received PCC decision. In this step, the PDN GW initiates aDeactive SAE Bearer Request to a serving GW.

In Step S1903, the serving GW initiates a Deactive SAE Bearer Request toan MME.

In Step S1904, the MME initiates a Deactive Bearer Request to an eNodeB.

In Step S1905, the eNodeB initiates a Deactive Radio Bearer Request to aUE.

In Step S1906, the UE removes a related uplink data stream template, andreturns a Deactive Radio Bearer Response to the eNodeB.

In Step S1907, the eNodeB returns a Deactive Bearer Response to the MME.

In Step S1908, the MME returns a Deactive SAE Bearer Response to theserving GW.

In Step S1908 a, the MME deregisters a PDN GW address in an HSS/SPR.Before the deregistration, the MME may determine whether the MME needsto deregister the PDN GW address in the HSS/SPR or not according tosubscription data of the UE and a parameter configured on the MME.

In Step S1909, the serving GW returns a Deactive SAE Bearer Response tothe PDN GW.

In Step S1910, the PDN GW returns a PCC Provision Ack to the PCRF, andtriggers the PCRF to deregister the address of the PDN GW from theHSS/SPR.

Step S1908 and Step S1908 a are performed in no particular order, inother words, Step S1908 a may be performed at any time after Step S1907.

If the network allows a terminal to use multiple PDNs, the HSS may havestored a corresponding relation between the PDN GW and an APN; and atthis time, the deregistration process of the PDN GW further includesdeleting the corresponding relation between the PDN GW address and theAPN stored in the HS S/SPR.

In addition, the embodiment shown in FIG. 19 may include scenarios wherethe UE terminates a service in a non-3GPP network, for example, multiplePDN and multiple HA scenarios, and may also include scenarios where thePDN GW initiates a bearer deletion process. When all services related tothe UE on the PDN GW are terminated, an entity such as an ePDG or an ASNGW that is equivalent to the MME may deregister the address of the PDNGW from the HSS/AAA server/SPR. If the AAA server and the HSS areseparate entities, the deregistration parameter or information needs tobe transmitted by the AAA server to the HSS.

The embodiment shown in FIG. 21 describes a process for deleting anaddress of a PDN GW from an HSS when a network initiates a bearerrelease process in a 3GPP access network. Specifically, when all bearersrelated to a UE on a PDN GW are released, an SGSN deletes an address ofthe PDN GW stored in an HSS/SPR.

In Step S2101, a PCRF provides a PCC decision to a PDN GW.

In Step S2102, the PDN GW triggers a bearer deletion process accordingto the received PCC decision. In this step, the PDN GW initiates aDeactive SAE Bearer Request to a serving GW.

In Step S2103, the serving GW initiates a Delete PDP Context Request toan SGSN.

In Step S2104, the SGSN initiates a Delete PDP Context Request to a UE.

In Step S2105, the UE returns a Delete PDP Context Response to the SGSN.

In Step S2106, the SGSN returns a Delete PDP Context Response to theserving GW.

In Step S2106 a, the SGSN deregisters an address of the PDN GW stored inan HSS/SPR.

In Step S2107, the SGSN returns a Deactive SAE Bearer Response to thePDN GW.

In Step S2108, the PDN GW returns a PCC Provision Ack to the PCRF.

In addition, when a network entity such as the PCRF initiates a bearerdeletion process, the PCRF may directly deregister the related PDN GWaddress from the HSS/AAA server/SPR. The specific process is basicallythe same as the embodiments provided herein, so the details will not bedescribed herein again.

If the network allows a terminal to use multiple PDNs, the HSS may havestored a corresponding relation between the PDN GW and an APN; and atthis time, the deregistration process of the PDN GW further includesdeleting the corresponding relation between the PDN GW address and theAPN stored in the HSS/SPR.

The embodiment shown in FIG. 20 describes a process for deleting anaddress of a PDN GW from an HSS when an HSS initiates a bearer releaseprocess in an SAE/LTE access network. In actual applications, a terminalmay subscribe to or unsubscribe from a service through a subscriptionmode such as the short message service; and when the terminalunsubscribes from the service, the terminal needs to check whether theservice is being used or not in time, and unsubscribe from the serviceat the bearer level in time, so an HSS needs to initiate a bearerrelease process.

Specifically, as shown in FIG. 20, the process includes the followingsteps.

In Step S2001, an HSS/AAA server/SPR initiates a Deactive SAE BearerRequest to a new MME.

In Step S2002, the new MME initiates a Deactive SAE Bearer Request to aserving GW.

In Step S2003, the serving GW initiates a Deactive SAE Bearer Request toa PDN GW.

In Step S2004, the PDN GW interacts with a PCRF to release relatedbinding information. This step is optional, and includes local breakoutscenarios, that is, the PDN GW interacts with an H-PCRF through aV-PCRF.

In Step S2005, the PDN GW returns a Deactive SAE Bearer Response to theserving GW.

In Step S2006, the serving GW returns a Deactive SAE Bearer Response tothe new MME.

In Step S2006 a, the new MME returns a Deactive SAE Bearer Response tothe HSS/SPR so as to deregister an address of the PDN GW in the HSS/SPR.Before the deregistration, the new MME may determine whether toderegister the PDN GW address from the HSS/SPR or not according tosubscription data of the UE or a parameter configured on the new MME.

The network entity that deregisters the PDG GW may be, but is notlimited to, the MME, PDN GW, PCRF, ePDG, ASN GW, or serving GW.

It should also be noted that, the HSS may have deregistered informationrelated to the PDN GW when initiating the bearer deletion process, sothe subsequent process for deregistering the address by differententities is optional.

In Step S2007, the new MME initiates a Deactive SAE Bearer Request tothe UE. In addition, the new MME may also indicate an eNodeB to releasea related radio bearer. Definitely, the indication may also be sentafter Step S2002.

In Step S2008, the UE returns a Deactive SAE Bearer Response to the newMME.

The embodiment shown in FIG. 20 may include scenarios where the UEterminates a service in a non-3GPP network, the bearer release processmay be initiated by a network service entity such as an HSS or an AAAserver, an entity such as an ePDG or an ASN GW that is equivalent to theMME or the PDN GW may deregister the PDN GW address from HSS/AAAserver/SPR, and the PDN GW address may also be deregistered through aPCC system. If the AAA server and the HSS are separate entities, thederegistration parameter or information needs to be transmitted by theAAA server to the HSS.

As some of the above embodiments are applicable to a communicationsystem, the present disclosure further provides embodiments of thecommunication system.

Consistent with an embodiment, the present disclosure provides acommunication system. The communication system includes an addressdeletion notification entity and a deregistration entity. The addressdeletion notification entity is configured to send a notification fordeleting an address of a network anchor point when the network anchorpoint no longer serves a terminal, in which the address of the networkanchor point has been registered with a network server. Thederegistration entity is configured to deregister the address of thenetwork anchor point according to the notification of the addressdeletion notification entity.

The deregistration entity is further configured to delete an APNcorresponding to the anchor point when the APN is registered with thenetwork server. The address deletion notification entity is an MME, oran SGSN, or an access network entity, or the network anchor point, or anentity in a PCC system.

As for the process for storing an address of a network anchor point to anetwork server by using the communication system, reference may be madeto the descriptions in the above method embodiments.

In actual applications, in order to effectively manage and utilize thenetwork resources, complete network management and control mechanismsare established for telecommunication networks. When a terminal logs outof a network, resources allocated to the terminal need to be released intime, including radio channels, bearers, and various tunnels.Accordingly, related management information such as an address of a PDNGW stored in an HSS also needs to be deleted. Therefore, the presentdisclosure further provides embodiments for a terminal to log out of anetwork.

In order to enable those skilled in the art to easily implement orreproduce a terminal to log out of a network, several embodiments areintroduced below with reference to the accompanying drawings.

Embodiments shown in FIGS. 22, 23, 24, 25, 26, 27, and 28 respectivelydescribe processes for a terminal to log out of a network when theterminal accesses through a non-3GPP access network.

Specifically, in the embodiment shown in FIG. 22, a UE initiates alogout process. In this embodiment, the UE accesses two PDNs at the sametime, and the UE uses a home address 1 (HoA1) to access a PDN 1identified by an APN1, and uses an HoA2 to access a PDN 2 identified byan APN 2.

As shown in FIG. 22, the logout process initiated by the UE includes thefollowing steps.

In Step 2201, an access gateway/ePDG receives a Tunnel Release Requestmessage sent by a UE. The message may carry an UE address and otherparameters.

In Step 2202, the access gateway/ePDG sends a Binding Update message toa PDN GW. In the message, a lifetime parameter is set to 0, and acare-of address (CoA) parameter is set to the HoA1, indicating that allbindings corresponding to the HoA1 need to be deregistered.

In Step 2203, the PDN GW instructs an AAA server/HSS to deregister PDNGW address information corresponding to the APN1.

Here, in Step 2203, the access gateway/ePDG may also instruct the AAAserver/HSS to deregister the PDN GW address information. In this case,Step 2203 may be performed concurrently with Steps 2202 and 2204.

In Step 2204, the PDN GW sends a Binding Update Ack message to theaccess gateway/ePDG to acknowledge that all bindings corresponding tothe HoA1 are deleted. The PDN GW and the access gateway/ePDG delete thebindings specified in Step 2202.

In Step 2205, the access gateway/ePDG sends a Binding Update message tothe PDN GW. In the message, a lifetime parameter is set to 0, and a CoAparameter is set to the HoA2, indicating that all bindings correspondingto the HoA2 need to be deregistered.

In Step 2206, the PDN GW instructs the AAA server/HSS to deregister PDNGW address information corresponding to the APN2.

Here, in Step 2206, the access gateway/ePDG may also instruct the AAAserver/HSS to deregister the PDN GW address information. In this case,Step 2206 may be performed concurrently with Steps 2205 and 2207.

In Step 2207, the PDN GW sends a Binding Update Ack message to theaccess gateway/ePDG to acknowledge that all bindings corresponding tothe HoA2 are deleted. The PDN GW and the access gateway/ePDG delete thebindings specified in Step 2205.

In Step 2208, the access gateway/ePDG returns a Tunnel Release Ackmessage to the UE. If the UE indicates in the Tunnel Release Requestmessage that the logout process is initiated due to power off, Step 2208may be omitted.

A resource release process is performed to release resources between theUE and the access gateway/ePDG.

If the UE and the ePDG are connected through a secure tunnel, Steps 2201and 2208 may be a Tunnel Release Request/Ack message. If a Layer 3connection such as an IP-based connection is established between the UEand the access gateway, Steps 2201 and 2208 may be a Layer 3-basedTrigger/Ack message or Trigger/Ack process, or an accesstechnology-specific trigger process.

If UE has multiple HoAs, bindings and PDN GW address informationcorresponding to each HoA may be sequentially deleted according to themethod of this embodiment. The above method for deregistering the PDN GWaddress information by using HoA as the granularity is also applicableto other embodiments.

Specifically, in the embodiment shown in FIG. 23, an access gateway/ePDGinitiates a logout process.

As shown in FIG. 23, the process includes the following steps.

In Step 2301, an access gateway/ePDG sends a Tunnel Release Requestmessage to a UE to request the releasing of a tunnel. The message maycontain a release reason and other parameters.

In Step 2302, the UE returns a Tunnel Release Ack message to the accessgateway/ePDG to perform a resource release process, so as to releasetunnel resources and access network resources between the UE and theaccess gateway/ePDG.

Here, the access gateway/ePDG may directly perform the resource releaseprocess without notifying the UE, that is, Steps 2301 and 2302 may beomitted.

If the UE and the access gateway/ePDG are connected through a securetunnel, Steps 2301 and 2302 may be a Tunnel Release Request/Ack message.If a Layer 3 connection such as an IP-based connection is establishedbetween the UE and the access gateway, Steps 2301 and 2302 may be aLayer 3-based Trigger/Ack message or Trigger/Ack process, or an accesstechnology-specific trigger process.

In Step 2303, the access gateway/ePDG sends a Binding Update message toa PDN GW. In the message, a lifetime parameter is set to 0, and a CoAparameter is set to an HoA, indicating that all bindings correspondingto the HoA need to be deregistered.

In Step 2304, the PDN GW returns a Binding Update Ack message to theaccess gateway/ePDG. The PDN GW and the access gateway/ePDG delete thebindings specified in Step 3.

In Step 2305, the PDN GW instructs an AAA server/HSS to deregister PDNGW address information.

If the network allows a terminal to use multiple PDNs, the AAAserver/HSS may have stored a corresponding relation between the PDN GWand an APN; and at this time, the deregistration process of the PDN GWfurther includes deleting the corresponding relation between the PDN GWaddress and the APN stored in the AAA server/HSS.

Here, in Step 2305, the access gateway/ePDG may also instruct the AAAserver/HSS to deregister the PDN GW address information.

Moreover, there is no strict time sequence among Steps 2301 and 2302,Steps 2303 and 2304, and Step 2305.

Specifically, in the embodiment shown in FIG. 24, a PDN GW initiates alogout process.

As shown in FIG. 24, the process includes the following steps.

In Step 2401, a PDN GW sends a Binding Revocation Indication message toan access gateway/ePDG. The message may contain the followingparameters: a UE identifier, a revocation reason, a revocation type, andthe like.

In Step 2402, the access gateway/ePDG sends a Tunnel Release Requestmessage to a UE. The message may contain a release reason and otherparameters.

In Step 2403, the UE returns a Tunnel Release Ack message to the accessgateway/ePDG to perform a resource release process, so as to releaseresources between the UE and the access gateway/ePDG.

Here, the access gateway/ePDG may directly perform the resource releaseprocess without notifying the UE, that is, Steps 2402 and 2403 may beomitted.

If the UE and the ePDG are connected through a secure tunnel, Steps 2402and 2403 may be a Tunnel Release Request/Ack message. If a Layer 3connection such as an IP-based connection is established between the UEand the access gateway, Steps 2402 and 2403 may be a Layer 3-basedTrigger/Ack message or Trigger/Ack process, or an accesstechnology-specific trigger process.

In Step 2404, the access gateway/ePDG returns a Binding Revocation Ackmessage to the PDN GW. The access gateway/ePDG and the PDN GW delete allbindings specified in Step 1.

In Step 2405, the PDN GW instructs an AAA server/HSS to deregister PDNGW address information.

If the network allows a terminal to use multiple PDNs, the AAAserver/HSS may have stored a corresponding relation between the PDN GWand an APN; and at this time, the deregistration process of the PDN GWfurther includes deleting the corresponding relation between the PDN GWaddress and the APN stored in the AAA server/HSS.

Here, in Step 2405, the access gateway/ePDG may also instruct the AAAserver/HSS to deregister the association information.

Specifically, in the embodiment shown in FIG. 25, an AAA server/HSSinitiates a logout process to a PDN GW.

As shown in FIG. 25, the process includes the following steps.

In Step 2501, an AAA server/HSS sends a Session Termination message to aPDN GW. The message may contain the following parameters: a UEidentifier, a termination reason, a termination type, and the like.

In Step 2502, the PDN GW sends a Binding Revocation Indication messageto an access gateway. The message may contain the following parameters:a UE identifier, a termination reason, a termination type, and the like.

In Step 2503, the access gateway sends a Tunnel Release Request messageto a UE.

In Step 2504, the UE returns a Tunnel Release Ack message to the accessgateway. An access network-specific resource release process isperformed to release access network resources.

Here, the access gateway/ePDG may directly perform the resource releaseprocess without notifying the UE, that is, Steps 2503 and 2504 may notbe performed.

If the UE and the access gateway/ePDG are connected through a securetunnel, Steps 2503 and 2504 may be a Tunnel Release Request/Ack message.If a Layer 3 connection such as an IP-based connection is establishedbetween the UE and the access gateway, Steps 2503 and 2504 may be aLayer 3-based Trigger/Ack message or Trigger/Ack process, or an accesstechnology-specific trigger process.

In Step 2505, the access gateway returns a Binding Revocation Ackmessage to the PDN GW. The access gateway and the PDN GW delete allbindings specified in Step 2502.

In Step 2506, the PDN GW instructs the AAA server/HSS to deregister PDNGW address information.

If the network allows a terminal to use multiple PDNs, the AAAserver/HSS may have stored a corresponding relation between the PDN GWand an APN; and at this time, the deregistration process of the PDN GWfurther includes deleting the corresponding relation between the PDN GWaddress and the APN stored in the AAA server/HSS.

Specifically, in the embodiment shown in FIG. 26, an AAA server/HSSinitiates a logout process to an access gateway/ePDG. As shown in FIG.26, the process includes the following steps.

In Step 2601, an AAA server/HSS sends a Session Termination message toan ePDG. The message contains the following parameters: a UE identifier,a termination reason, a termination type, and the like.

In Step 2602, the access gateway/ePDG sends a Tunnel Release Requestmessage to a UE. The message may contain a release reason and otherparameters.

In Step 2603, the UE returns a Tunnel Release Ack message to the accessgateway/ePDG to perform a resource release process, so as to releaseresources between the UE and the access gateway/ePDG.

Here, the access gateway/ePDG may directly perform the resource releaseprocess without notifying the UE, that is, Steps 2602 and 2603 may notbe performed.

If the UE and the ePDG are connected through a secure tunnel, Steps 2602and 2603 may be a Tunnel Release Request/Ack message. If a Layer 3connection such as an IP-based connection is established between the UEand the access gateway, Steps 2602 and 2603 may be a Layer 3-basedTrigger/Ack message or Trigger/Ack process, or an accesstechnology-specific trigger process.

In Step 2604, the access gateway/ePDG sends a Binding Update message toa PDN GW. In the message, a lifetime parameter is set to 0, and a CoAparameter is set to an HoA, indicating that all bindings correspondingto the HoA need to be deregistered.

In Step 2605, the PDN GW returns a Binding Update Ack message to theePDG. The PDN GW and the access gateway/ePDG delete all bindingsspecified in Step 2604.

In Step 2606, the access gateway/ePDG returns a Session Termination Ackmessage to the AAA server/HSS. After receiving the message, the AAAserver/HSS deregisters association information, for example, addressinformation of the PDN GW that provides a service to the UE. If thenetwork allows a terminal to use multiple PDNs, the AAA server/HSS mayhave stored a corresponding relation between the PDN GW and an APN; andat this time, the AAA server/HSS may further delete the correspondingrelation between the PDN GW address and the APN stored therein.

Specifically, in the embodiment shown in FIG. 27, in the case of clientmobile IP (CMIP) in a co-located CoA (Co-CoA mode), a UE initiates alogout process. The CMIP is a terminal-based mobile IP technology, thatis, a technology that requires a terminal to participate in a mobile IPbinding process. The CMIP has two modes: a foreign agent CoA mode(FA-CoA mode) and the Co-CoA mode. In the FA-CoA mode, a CoA of aterminal is an IP address of an access link mobile agent, and at thistime, two endpoints of a mobile IP tunnel is the access link mobileagent and a home link mobile agent. In the Co-CoA mode, a CoA of aterminal is a terminal IP address obtained in a certain manner, and atthis time, two endpoints of a mobile IP tunnel is the terminal and ahome link mobile agent, and an access link mobile agent just serves asan ordinary router, that is, a mobile agent may not be deployed in anaccess link.

As shown in FIG. 27, the process includes the following steps.

In Step 2701, a PDN GW receives a Binding Update Request message sent bya UE. In the message, a lifetime parameter is set to 0, and a CoAparameter is set to an HoA, indicating that all bindings correspondingto the HoA need to be deregistered.

In Step 2702, the PDN GW returns a Binding Update Ack message to the UE.

The UE and the PDN GW delete the binding relation between the HoA andthe CoA, and release a CMIP tunnel.

In Step 2703, the PDN GW instructs an AAA server/HSS to deregister PDNGW address information.

If the network allows a terminal to use multiple PDNs, the AAAserver/HSS may have stored a corresponding relation between the PDN GWand an APN; and at this time, the deregistration process of the PDN GWfurther includes deleting the corresponding relation between the PDN GWaddress and the APN stored in the AAA server/HSS.

In Step 2704 a, the PDN GW instructs an access gateway/ePDG to releaseaccess link resources. Alternatively, after Step 2703, the AAAserver/HSS instructs the access gateway/ePDG to release the access linkresources (Step 2704 b).

In Step 2705, after receiving the indication of releasing the accesslink resources, the access gateway/ePDG instructs the AAA server/HS S toderegister the PDN GW address information.

If the network allows a terminal to use multiple PDNs, the AAAserver/HSS may have stored a corresponding relation between the PDN GWand an APN; and at this time, the deregistration process of the PDN GWfurther includes deleting the corresponding relation between the PDN GWaddress and the APN stored in the AAA server/HSS.

Here, Step 2703 and Step 2705 are two manners for deleting associationinformation on the AAA server/HSS, and this embodiment may beimplemented by performing either of the two steps.

Specifically, in the embodiment shown in FIG. 28, in the case of CMIP inthe Co-CoA mode, a PDN GW initiates a logout process. As shown in FIG.28, the process includes the following steps.

In Step 2801, a PDN GW sends a Binding Revocation Indication to a UE.

In Step 2802, the UE returns a Binding Revocation Ack message to the PDNGW.

The UE and the PDN GW delete the binding relation between the HoA andthe CoA, and release a CMIP tunnel.

In Step 2803, the PDN GW instructs an AAA server/HSS to deregister PDNGW address information.

If the network allows a terminal to use multiple PDNs, the AAAserver/HSS may have stored a corresponding relation between the PDN GWand an APN; and at this time, the deregistration process of the PDN GWfurther includes deleting the corresponding relation between the PDN GWaddress and the APN stored in the AAA server/HSS.

In Step 2804 a, the PDN GW instructs an access gateway/ePDG to releaseaccess link resources. Alternatively, after Step 2803, the AAAserver/HSS instructs the access gateway/ePDG to release the access linkresources (Step 2804 b).

In Step 2805, after receiving the indication of releasing the accesslink resources, the access gateway/ePDG instructs the AAA server/HSS toderegister the PDN GW address information. If the network allows aterminal to use multiple PDNs, the AAA server/HSS may have stored acorresponding relation between the PDN GW and an APN; and at this time,the deregistration process of the PDN GW further includes deleting thecorresponding relation between the PDN GW address and the APN stored inthe AAA server/HSS.

Here, Step 2803 and Step 2805 are two manners for deleting associationinformation on the AAA server/HSS, and this embodiment may beimplemented by performing either of the two steps.

Embodiments shown in FIGS. 29, 30, 31, and 32 respectively describeprocesses for a terminal to log out of a network when the terminalaccesses an evolved 3GPP core network through a 3GPP network.

Specifically, in the embodiment shown in FIG. 29, a serving GW initiatesa logout process. As shown in FIG. 29, the process includes thefollowing steps.

In Step 2901, a serving GW sends a Logout Request message to an MME. Themessage may contain a UE identifier, a logout reason, a logout type, andother parameters.

In Step 2902, the MME sends a Logout Request message to an eNodeB. Themessage may contain a UE identifier, a logout reason, a logout type, andother parameters.

In Step 2903, the eNodeB sends a Logout Request message to a UE. Themessage may contain a logout reason, a logout type, and the like.

In Step 2904, the UE returns a Logout Ack message to the eNodeB.

Radio resources between the UE and the eNodeB are released.

Here, the eNodeB may directly release the radio resources withoutnotifying the UE, that is, Steps 2903 and 2904 may be omitted.

In Step 2905, the eNodeB returns a Logout Ack message to the MME.

In Step 2906, the MME returns a Logout Ack message to the serving GW.

Resources between the eNodeB and the serving GW are released.

In Step 2907, the serving GW sends a Binding Update message to a PDN GW.In the message, a lifetime parameter is set to 0, and a CoA parameter isset to an HoA, indicating that all bindings corresponding to the HoAneed to be deregistered.

In Step 2908, the PDN GW instructs an AAA server/HSS to deregister PDNGW address information.

If the UE accesses multiple PDNs at the same time, i.e., the UE hasmultiple HoAs, the PDN GW may be indicated to delete all bindingscorresponding to all HoAs of the UE in Step 2907, and then the PDN GWinstructs the AAA server/HSS to deregister all PDN GW addressinformation of the UE in Step 2908; the PDN GW may be instructed tosequentially delete bindings corresponding to each HoA, and the PDN GWsequentially instructs the AAA server/HSS to deregister PDN GW addressinformation corresponding to each APN according to the method in theembodiment shown in FIG. 22.

Here, in Step 2908, the serving GW or the MME may also instruct the AAAserver/HSS to deregister the PDN GW address information.

In Step 2909, the PDN GW returns a Binding Update Ack message to theserving GW.

The PDN GW and the serving GW delete all bindings specified in Step2907.

Specifically, in the embodiment shown in FIG. 30, a PDN GW or an AAAserver/HSS initiates a logout process. As shown in FIG. 30, the processincludes the following steps.

In Step 3001 a, a PDN GW sends a Binding Revocation Indication messageto a serving GW. The message may contain the following parameters: a UEidentifier, a revocation reason, a revocation type, and the like.

If an AAA server/HSS initiates a logout process, the AAA server/HSSsends a Logout Indication message to the PDN GW first (Step 3001 b), andthe PDN GW then sends the Binding Revocation Indication message to theserving GW.

In Step 3002, the serving GW sends a Logout Request message to an MME.The message may contain a UE identifier, a logout reason, a logout type,and other parameters.

In Step 3003, the MME sends a Logout Request message to an eNodeB. Themessage may contain a UE identifier, a logout reason, a logout type, andother parameters.

In Step 3004, the eNodeB sends a Logout Request message to a UE. Themessage may contain a logout reason, a logout type, and the like.

In Step 3005, the UE returns a Logout Ack message to the eNodeB, andradio resources between the UE and the eNodeB are released.

Here, the eNodeB may directly release the radio resources withoutnotifying the UE, that is, Steps 3004 and 3005 may be omitted.

In Step 3006, the eNodeB returns a Logout Ack message to the MME.

In Step 3007, the MME returns a Logout Ack message to the serving GW.

Resources between the eNodeB and the serving GW are released.

In Step 3008, the serving GW returns a Binding Revocation Ack message tothe PDN GW.

The PDN GW and the serving GW delete all bindings specified in Step3001.

In Step 3009, the PDN GW instructs the AAA server/HSS to deregister PDNGW address information.

If the network allows a terminal to use multiple PDNs, the AAAserver/HSS may have stored a corresponding relation between the PDN GWand an APN; and at this time, the deregistration process of the PDN GWfurther includes deleting the corresponding relation between the PDN GWaddress and the APN stored in the AAA server/HSS.

Here, in Step 3009, the serving GW or the MME may also instruct the AAAserver/HSS to deregister the PDN GW address information.

Specifically, in the embodiment shown in FIG. 31, an MME initiates alogout process. As shown in FIG. 31, the process includes the followingsteps.

In Step 3101, an MME sends a Logout Request message to an eNodeB. Themessage may contain a UE identifier, a logout reason, a logout type, andother parameters.

In Step 3102, the eNodeB sends a Logout Request message to a UE. Themessage may contain a logout reason, a logout type, and the like.

In Step 3103, the UE returns a Logout Ack message to the eNodeB.

Radio resources between the UE and the eNodeB are released.

Here, the eNodeB may directly release the radio resources withoutnotifying the UE, that is, Steps 3102 and 3103 may be omitted.

In Step 3104, the eNodeB returns a Logout Ack message to the MME.

In Step 3105, the MME sends a Logout Request message to a serving GW.

In Step 3106, the serving GW sends a Binding Update message to a PDN GW.In the message, a lifetime parameter is set to 0, and a CoA parameter isset to an HoA, indicating that all bindings corresponding to the HoAneed to be deregistered.

In Step 3107, the PDN GW instructs an AAA server/HSS to deregister PDNGW address information.

If the network allows a terminal to use multiple PDNs, the AAAserver/HSS may have stored a corresponding relation between the PDN GWand an APN; and at this time, the deregistration process of the PDN GWfurther includes deleting the corresponding relation between the PDN GWaddress and the APN stored in the AAA server/HSS.

Here, in Step 3107, the serving GW or the MME may also instruct the AAAserver/HSS to deregister the PDN GW address information.

In Step 3108, the PDN GW returns a Binding Update Ack message to theserving GW.

The PDN GW and the serving GW delete all bindings specified in Step3106.

In Step 3109, the serving GW returns a Logout Ack message to the MME.

Resources between the eNodeB and the serving GW are released.

Specifically, in the embodiment shown in FIG. 32, a UE initiates alogout process. As shown in FIG. 32, the process includes the followingsteps.

In Step 3201, an eNodeB receives a Logout Request message sent by a UE.The message may contain a UE identifier, a logout reason, a logout type,and other parameters.

In Step 3202, the eNodeB sends a Logout Request message to an MME. Themessage may contain a UE identifier, a logout reason, a logout type, andother parameters.

In Step 3203, the MME sends a Logout Request message to a serving GW.The message may contain a UE identifier, a logout reason, a logout type,and other parameters.

In Step 3204, the serving GW sends a Binding Update Request to a PDN GW.In the message, a lifetime parameter is set to 0, and a CoA parameter isset to an HoA, indicating that all bindings corresponding to the HoAneed to be deregistered.

In Step 3205, the PDN GW instructs an AAA server/HSS to deregister PDNGW address information.

If the network allows a terminal to use multiple PDNs, the AAAserver/HSS may have stored a corresponding relation between the PDN GWand an APN; and at this time, the deregistration process of the PDN GWfurther includes deleting the corresponding relation between the PDN GWaddress and the APN stored in the AAA server/HSS.

Here, in Step 3205, the serving GW or the MME may also instruct the AAAserver/HSS to deregister the PDN GW address information.

In Step 3206, the PDN GW returns a Binding Update Ack message to theserving GW.

The serving GW and the PDN GW delete all bindings specified in Step 4.

In Step 3207, the serving GW returns a Logout Ack message to the MME.

In Step 3208, the MME returns a Logout Ack message to the eNodeB, andresources between the eNodeB and the serving GW are released.

In Step 3209, the eNodeB returns a Logout Ack message to the UE, andreleases radio resources.

A method for a terminal to log out of a network so as to releaseresources is provided according to some embodiments described herein foran evolved network in which broadband radio access and mobilecommunication networks are converged. In the evolved network, when aterminal needs to be disconnected from the network, or the networkintends to disconnect from the terminal, network resources can bereleased in time. Therefore, management and control mechanisms of theevolved network may be enhanced, thus improving the resourceutilization.

The above descriptions are merely embodiments of the present disclosure.It will be apparent to those skilled in the art that improvements andmodifications can be made to the embodiments described in the presentdisclosure without departing from the principle of the presentdisclosure, and such improvements and modifications shall fall withinthe protective scope of the present disclosure.

What is claimed is:
 1. A telecommunication method, comprising:determining, by a network apparatus, whether to register information ofa network anchor point and an access point name (APN) corresponding tothe network anchor point to a network server according to a certaincondition, wherein the certain condition comprises subscription data ofa user equipment (UE) indicates that the UE is allowed to hand over to anon-3rd Generation Partnership Project (non-3GPP) access; registering,by the network apparatus, the information of the network anchor pointand the APN to the network server, when determining to register theinformation of the network anchor point and the APN to the networkserver; and storing, by the network server, the information of thenetwork anchor point and the APN.
 2. The method of claim 1, wherein thenetwork apparatus comprises a mobility management entity (MME).
 3. Themethod of claim 1, wherein the network server comprises a homesubscriber server (HSS).
 4. The method of claim 2, wherein the networkserver comprises a home subscriber server (HSS).
 5. The method of claim4, wherein the method is applied in an initial attach procedure of theUE to a 3rd Generation Partnership Project (3GPP) network.
 6. The methodof claim 5, wherein the 3GPP network comprises a long term evolution(LTE)/System Architecture Evolution (SAE) network.
 7. The method ofclaim 4, wherein registering the address information of the networkanchor point and the APN comprises: registering, by the networkapparatus, the address information of the network anchor point and theAPN to the network server in case that a bearer in a 3rd GenerationPartnership Project (3GPP) network was established by the network anchorpoint.
 8. The method of claim 7, wherein the 3GPP network comprises along term evolution (LTE)/System Architecture Evolution (SAE) network.9. The method of claim 4, wherein the method is applied in an initialpacket data network (PDN) connectivity establishment procedure.
 10. Themethod of claim 1, wherein the network anchor point comprises a packetdata network gateway (PDN GW).
 11. The method of claim 4, wherein theinformation of the network anchor point comprises an internet protocol(IP) address of the network anchor point.
 12. The method of claim 4,wherein the information of the network anchor point comprises a fullyqualified domain name (FQDN) of the network anchor point.
 13. Atelecommunication system, comprising: a network apparatus; and a networkserver capable of communicatively connecting with the network apparatus,wherein the network apparatus is configured to determine, according to acertain condition, whether to register information of a network anchorpoint and an access point name (APN) corresponding to the network anchorpoint to the network server; and to register the information of thenetwork anchor point and the APN to the network server, when determiningto register the information of the network anchor point and the APN tothe network server, wherein the certain condition comprises subscriptiondata of a user equipment (UE) indicates that the UE is allowed to handover to a non-3rd Generation Partnership Project (non-3GPP) access;wherein the network server is configured to store the information of thenetwork anchor point and the APN.
 14. The system of claim 13, whereinthe network apparatus is a mobility management entity (MME).
 15. Thesystem of claim 13, wherein the network server comprises a homesubscriber server (HSS).
 16. The system of claim 14, wherein the networkserver comprises a home subscriber server (HSS).
 17. The system of claim16, wherein the network apparatus is configured to register the addressinformation of the network anchor point and the APN to the networkserver in an initial attach procedure of the UE to a 3rd GenerationPartnership Project (3GPP) network.
 18. The system of claim 17, whereinthe 3GPP network comprises a long term evolution (LTE)/SystemArchitecture Evolution (SAE) network.
 19. The system of claim 16,wherein the network apparatus is configured to register the addressinformation of the network anchor point and the APN to the networkserver in case that a bearer in a 3rd Generation Partnership Project(3GPP) network was established by the network anchor point.
 20. Thesystem of claim 19, wherein the 3GPP network comprises a long termevolution (LTE)/System Architecture Evolution (SAE) network.
 21. Thesystem of claim 16, wherein the network apparatus is configured toregister the address information of the network anchor point and the APNto the network server in an initial packet data network (PDN)connectivity establishment procedure.
 22. The system of claim 13,wherein the network anchor point comprises a packet data network gateway(PDN GW).
 23. The system of claim 16, wherein the information of thenetwork anchor point comprises an internet protocol (IP) address of thenetwork anchor point.
 24. The system of claim 16, wherein theinformation of the network anchor point comprises a fully qualifieddomain name (FQDN) of the network anchor point.